函数式范式将开发者的思维模式从“更新一个有状态的盒子”转变为 应用数学变换 到不可变值。在 Elixir 中，数据永远不会被改变；它只会以新的形式重生。
1. 数学断言
当你写下 $x = a + 1$ 时，你并不是将结果赋给一个变量。相反，你只是在 断言 表达式 $x$ 与 $a + 1$ 具有相同值。这与代数逻辑一致，其中 $x$ 在特定上下文中代表一个固定值。
2. 不可变性作为保障
在 Elixir 中， 所有值都是不可变的数据一旦创建便无法被更改。这消除了函数可能意外修改全局变量或传入对象的“副作用”，确保代码具有可预测性且线程安全。
3. 转换与修改
我们从不在原地修改数据。Elixir 没有赋值操作；相反，它试图 将值与模式匹配。要“改变”一个值，我们通过函数传递原始数据，生成一个全新的版本。
iex> name = "elixir"
"elixir"
iex> cap_name = String.capitalize name
"Elixir"
iex> name
"elixir"（仍然完好无损！）
"elixir"
iex> cap_name = String.capitalize name
"Elixir"
iex> name
"elixir"（仍然完好无损！）
main.py
TERMINALbash — 80x24
> Ready. Click "Run" to execute.
>
QUESTION 1
In Elixir, what does the expression
x = a + 1 represent?A command to allocate a new memory box for x.
An assertion that x and a + 1 have the same value.
A mutable assignment operator.
A way to delete the previous value of a.
✅ Correct!
Correct! In functional programming, the equals sign is a match/assertion, not an assignment.❌ Incorrect
Elixir uses matching. You are declaring that both sides are equal, not commanding a state change.QUESTION 2
What is the result of
name after executing cap_name = String.capitalize(name)?The value of 'name' is updated to start with a capital letter.
The 'name' variable is deleted from memory.
The value of 'name' remains exactly as it was originally created.
An error occurs because you cannot re-use 'name'.
✅ Correct!
Because data is immutable, String.capitalize creates a *new* string; the original 'name' is untouched.❌ Incorrect
Recall the rule: data cannot be altered once created. Any transformation results in a new value.QUESTION 3
Which of these statements is a core Logic Rule of Elixir?
Data should be modified in place for performance.
All values are immutable.
Variables are global by default.
Strings can be appended to directly.
✅ Correct!
Immutability is the foundational guarantee of Elixir and the BEAM VM.❌ Incorrect
In functional languages, we never modify data in place; we only transform it.QUESTION 4
Why is immutability beneficial for concurrent programming?
It requires more RAM, which makes systems faster.
It allows multiple threads to change data simultaneously.
It eliminates race conditions because data cannot be changed under your feet.
It automatically recompiles the code.
✅ Correct!
If data cannot change, you don't need complex locks or mutexes to prevent corruption.❌ Incorrect
Think about 'side effects'. If data is immutable, no other part of the system can change what you are looking at.QUESTION 5
What happens in Snippet 2:
array = [1,2,3]; do_something_with(array); print(array)?The output is guaranteed to be [1,2,3].
The output depends on what do_something_with does.
The output will be empty if the function sorted the list.
The array is cleared from memory.
✅ Correct!
Predictability is the default. Since Elixir lacks in-place modification, the array remains [1,2,3].❌ Incorrect
Even if the function 'modifies' the array, it only returns a NEW version. The original binding is safe.Case Study: The Predictable System
Immutability in Practice
You are debugging a legacy system where a list of user IDs is passed through five different processing functions. In an imperative language, you are worried one function might be clearing the list. In Elixir, you see the following code:
count = 99
process_data(count)
IO.puts count
Q
Explain why the output of IO.puts count is guaranteed to be 99 regardless of what process_data does.
Solution:
Because all values in Elixir are immutable. The variable 'count' points to the integer 99. When passed to 'process_data', the function receives a copy of the value (or a reference to the immutable data). Since Elixir does not have assignment and cannot modify memory in place, 'process_data' cannot overwrite the memory location of 'count'.
Because all values in Elixir are immutable. The variable 'count' points to the integer 99. When passed to 'process_data', the function receives a copy of the value (or a reference to the immutable data). Since Elixir does not have assignment and cannot modify memory in place, 'process_data' cannot overwrite the memory location of 'count'.
Q
If process_data needs to increment the count, how would it return that value to the caller?
Solution:
The function must return the NEW transformed value. The caller would then need to bind that result to a new variable name (e.g., `new_count = process_data(count)`) or rebind the existing label if appropriate within that scope.
The function must return the NEW transformed value. The caller would then need to bind that result to a new variable name (e.g., `new_count = process_data(count)`) or rebind the existing label if appropriate within that scope.